Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: augment tokenID to token vending machine #978

Merged
merged 4 commits into from
Oct 24, 2023
Merged

Conversation

pratik151192
Copy link
Contributor

@pratik151192 pratik151192 commented Oct 24, 2023

Added tokenId to TVM examples. I have demonstrated this as a query string parameter as a generic tokenId was not making sense but let me know if there's a better way to demonstrate this.

@pratik151192 pratik151192 requested review from cprice404, anitarua and allenheltondev and removed request for cprice404 October 24, 2023 13:30
@pratik151192 pratik151192 marked this pull request as ready for review October 24, 2023 13:48
Copy link

@allenheltondev allenheltondev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the small change in the readme

examples/nodejs/token-vending-machine/README.md Outdated Show resolved Hide resolved
anitarua
anitarua previously approved these changes Oct 24, 2023
Copy link
Contributor

@anitarua anitarua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@pratik151192 pratik151192 dismissed allenheltondev’s stale review October 24, 2023 17:12

Addressed in a commit not sure why it doesnt mark as addressed

cprice404
cprice404 previously approved these changes Oct 24, 2023
Copy link
Contributor

@cprice404 cprice404 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one nit, not necessarily a blocker


You can also pass a tokenId as a query string to your curl command to add context to your token. This can be particularly useful when using [Momento Topics](https://www.gomomento.com/services/topics) as the tokenId can be retrieved from subscription messages, allowing your application to distinguish between different subscribers.

`https://9jkmukxn68.execute-api.us-west-2.amazonaws.com/prod?name=Taylor`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we be consistent in the name of the query param and what you say in the docs? you say tokenId and then the QP is name. kinda seems like the most clear thing to do is just have the QP be named tokenId as well. just a nit though, i don't feel too strongly

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll clarify that in this case the tokenId is the name. Good call out. The reason I want it to be more relatable to the real world is for customers to be able to derive some sense of the use case

@pratik151192 pratik151192 merged commit 336374a into main Oct 24, 2023
13 checks passed
@pratik151192 pratik151192 deleted the tvm-tokenId branch October 24, 2023 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants